4. Option 2: Set Up Your Own VMs on Windows 2008 R2
Rather than install Windows 2008 R2, provision it for Hyper-V, and create a
machine to import the 2010-7a VM, you have another option.
Architecture for Server Configuration
The following illustration shows what software is installed on what machines
for the configuration . To ensure that
our configuration could be duplicated by readers, we used 180-day trial versions
for all software.
The numbered items in the following list correspond to the circled areas in
the image:
-
Host machine:
. Your host machine is the machine on which you need to install
Windows Server 2008 R2, either by using a physical DVD or installing
and learning to use ISO image software.
-
VM (or guest machine), MOSS-DC.contoso: Contains your Active Directory domain structure, in which you need
to create user accounts for your SharePoint, SQL Server roles, and
client roles, such as the Unattended Service account and SharePoint
Admin account. This machine becomes your domain, and it will
probably need a physical IP address. You will join the other VMs to
the domain.
-
Second VM (or guest machine), SP2010-BI: Includes Windows Server 2008 R2 + SQL Server 2008 R2 +
SharePoint 2010, in that order. Note that the databases for your
SharePoint Server are different from those used as data sources in
the exercises. Some people separate the two by creating a separate
instance for their data sources. Another option is to use a
different VM or a separate machine, as described in item 5 of this
list.
-
(Optional) Third VM:
. To truly test the user accounts and security of your
configuration, it is a good idea to create a VM that can play the
role of the client in test environment. On this VM, install Windows
7 and Office 2010.
Note
If you want to get serious about testing security configurations such as
Kerberos or NTLM, you should consider taking installation and configuration
to the next level by creating another VM to host the data sources, SQL
Server and 2008 R2 Analysis Services. Because memory resources are typically
scarce after running three VMs on a physical host machine, you might
consider adding another physical computer to your configuration that you can
allocate to Analysis Services data sources. The configuration options
available depend on the resources you have, such as memory and processor
speed.
Select a Host Computer with Windows 2008 R2
The computer you choose as the host matters, because it must have a Hyper-V
capable processor. In addition, you need enough processing power and memory to
run the VMs. You might also need to enable Hyper-V for your processor in the
system BIOS to make virtualization possible.
The first step is to locate the right processor. If you already have a
computer, check to see whether the processor is listed in the Hardware section
of the Windows Server catalog at
http://go.microsoft.com/fwlink/?LinkId=111228
. To see the list of servers that have been tested to run Hyper-V, in
the Hardware section of the Windows Server catalog, under Product category,
click Servers, and then under Additional Qualifications, click Hyper-V.
You can also review the more comprehensive documentation for Hyper-V by
reading the TechNet topic “Hyper-V Getting Started Guide,”
at
http://technet.microsoft.com/en-us/library/cc732470(WS.10).aspx
.
Install and Configure Windows 2008 R2 for Hyper-V
This section simply points you to useful links containing
instructions for installing Windows 2008 R2 and configuring your server for
Hyper-V.
Install Software on Your VMs
You should plan to install the following software on your
VMs.
Install Windows 2008 R2 on Your VMs
The authors recommend that you purchase and install mounting software so
that you can mount ISO images from which to install when you connect and
start your newly created VMs. You cannot access installation files easily
from the host machine unless you install the mounting software.
